Conversation
Extension release summary🚀 Will release on merge
See the contributing guide for details. |
| "minimumConnectVersion": "2025.04.0", | ||
| "requiredFeatures": ["API Publishing", "OAuth Integrations"], | ||
| "version": "0.0.6" | ||
| "version": "0.0.7" |
There was a problem hiding this comment.
It doesn't hurt anything to release this, but if it's only the readme that's changing, we don't actually need a release for that, right? the readme isn't in the thing that gets installed from the gallery for this one, right?
There was a problem hiding this comment.
Oh great point, I was on a roll. The readme goes with the bundle, so it does technically ( i had to check to confirm just now) but I am not sure that's really used?
There was a problem hiding this comment.
nods yeah I think it tags along, but the only way someone would get to it would be to download the bundle after installing.
There was a problem hiding this comment.
Seems unlikely. I will defer to your judgement here, it also kind of strange to bump version just for readme change now that we are talking about it.
| f"{one_tab}• Click <b>Add Variable</b><br>" | ||
| f"{one_tab}• Click <b>Save</b> at the top of the screen to save your changes<br><br>" | ||
| f"{one_tab}• Open the content settings for this report<br>" | ||
| f"{one_tab}• Set the environment variable <code>{var_name}</code> to the URL you copied in the previous step<br>" |
There was a problem hiding this comment.
Generic wording, no screenshots works for both old and new UI which is a good idea. One concern: for Content Health Monitor specifically, a first-time user deploying this extension sees "Open the content settings" and "Set the environment variable" without visual guidance may leave them searching for where things are.
Approach in #345 provides step by step instruction but won't match what the ~small number of users on the old settings pane see.
Since the new UI is enabled by default and the old UI is scheduled for removal in v2026.06.0 (#36191 in Connect), I'd lean toward targeting the new UI with specific instructions but the generic approach is reasonable too. Happy to go either way.
There was a problem hiding this comment.
late to this, since customers might be on older versions without new settings panel I lean towards keeping it generic to avoid confusion. I can add an issue to come back next year and add updates.
3 participants
Fixes #344
Fixes #346
With new content settings panel, some extensions have outdated READMEs and docs pointing to tabs that no longer exist. This was an attempt to update the docs to no reference specific tabs since customers will be on two different versions of the content settings panel.
I did try listing out both options (in the new Content settings panel go the XX tab and in the old go to XX tab) but it was clunky imo. Very open to suggestions with this!